Release 10.1A: OpenEdge Data Management:
DataServer for ODBC

Connecting a schema holder at startup

OpenEdge supports connection parameters that you can use to connect both the OpenEdge schema holder and an ODBC data source at startup. These parameters control how your system connects to a database. When the DataServer runs in a remote configuration, your startup command or parameter file must always include parameters that control networking options.

Table 4–1 describes the database connection parameters that you use when you connect to a schema holder and an ODBC data source through the DataServer.

Table 4–1: DataServer connection parameters

Parameter	Status	Description
Database Type ODBC (-dt ODBC)	Optional	Specifies that the type of the target data source is ODBC. Note that the data source must be a supported ODBC data source.
Physical Database Name (-db)	Required	Indicates the name by which OpenEdge recognizes the ODBC data source to which you want to connect. This name must match the name that you used when you registered the data source as an ODBC data source.
Logical Database Name (-ld)	Optional	Specifies the logical name of the ODBC data source. This is the name that you use to refer to the data source in your applications. You must use this parameter only when the logical data-source name differs from its physical name. This name should match the logical database name that you defined in your schema holder. For example, your applications might refer to the Sybase demo database as mydemo. In this case, the physical name is demo, and the logical name is mydemo.
Host Name (-H)	Required for remote DataServer	Indicates the name of the host machine in the network.
Service Name (-S)	Required for remote DataServer	Indicates the name of the service that you are calling. If you use the NameServer with Progress Explorer, specify the service name or IP address of the host machine where the NameServer resides. If you are using _probrkr.exe or the Progress Explorer without a NameServer, specify the service name or IP address of the host machine where the broker resides.
User ID (-U)	Required if the ODBC data source requires it	Supplies the login name that the DataServer uses to log into the ODBC data source.
Password (-P)	Required if the ODBC data source requires it	Supplies the password that the DataServer uses to log into the ODBC data source. Different login name and password combinations allow for different levels of user privileges.
Data Service (-DataService)	Required for Progress Explorer connections	Specifies the data service the NameServer uses. This must be used in conjunction with the -Dsrv option SVUB,1. For more information, see the "Starting and stopping a broker process from the Progress Explorer and connecting a client" section.
Single–User Mode (-1)	Optional	Specifies that a schema holder is used in single-user mode. Single–User Mode is the default unless a server is started for the schema holder.
Read-Only (-RO)	Optional	Specifies that a schema holder is read-only. Connecting a schema holder as read-only increases processing speed at client startup time. It also allows multiple client processes on the same machine to access the schema holder without starting additional server processes.
Local Cache (-cache)	Optional	Specifies that you are using a local cache file for the schema holder. Create the cache file with the SAVE CACHE COMPLETE statement.
DataServer (-Dsrv)	Optional	Specifies options with which you control your ODBC Driver and DataServer environment. See the "Query tuning with connection and startup parameters" section and the "ODBC options" section for more information. Note: When you specify a list of -Dsrv parameters, be sure not to include any spaces anywhere in this list.
Direct Connect (-DirectConnect)	Optional	Instructs the client to bypass the controlling NameServer and connect directly to the ODBC DataServer Broker.
Server Join (-nojoinbysqldb)	Optional	Specifies that the client evaluates and performs queries that have joins. This might slow performance, but it provides results that are consistent with OpenEdge behavior. Use -nojoinbysqldb at startup time.

You can create a parameter file for each database:

For a local DataServer, the parameter file must contain the -db parameter and can optionally contain the -Dsrv, -U, and -P connection parameters, depending on the requirements of the data service.
For a remote DataServer, the same parameter conditions apply as for a local DataServer. In addition, a remote connection must contain the -H and -S connection parameters.

You can add more startup and connection parameters than the ones listed—these are the typical parameters. For a complete list of parameters and for information on how to create a parameter file, see the OpenEdge Deployment: Startup Command and Parameter Reference .

Using a local DataServer configuration: examples

Use the following syntax starts OpenEdge:

In single-user mode.
In a local DataServer configuration.
With a local schema holder connected.
With an ODBC data source connected.

prowin32 -1 schema-holder-name -db datasrc-name -dt ODBC -ld logical-datasrc-name -U userID -P password -Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=server-name

You can type these commands on the command line of a program item property box.

The following example starts OpenEdge in a local DataServer configuration:

The schema holder’s physical name is odbholder and it is read-only.
The physical data-source name (and the ODBC data-source name) is sports.
The data-source type is ODBC.
The logical data-source name is mysport.
The user ID is bob.
The password is bobpass.
Assorted -Dsrv options are specified.

prowin32 -1 odbholder -RO -db sports -dt ODBC -ld mysport -U bob -P bobpass -Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=sqlserv1

Using a remote DataServer configuration: examples

A remote connection differs from a local connection in that it requires the Host (-H) and Service (-S) parameters.

Use the following command syntax to start OpenEdge:

In single-user mode.
In a remote-DataServer configuration.
With a local schema holder connected.
With an ODBC data source connected.

On a Windows client:

prowin32 schema-holder-name -db datasrc-name -dt ODBC -ld logical-datasrc-name -H hostname -S service-name -U userID -P password -Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=server-name

On a UNIX client:

pro schema-holder-name -db datasrc-name -dt ODBC -ld logical-datasrc-name -H hostname -S service-name -U userID -P password -Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=datasrc-name

The following examples start OpenEdge in a remote DataServer configuration. In these examples:

The schema holder’s physical name is odbholder and it is read-only.
The data-source name is sports.
The data-source type is ODBC.
The logical data-source name is mydemo.
The host name is host1.
The service name is odbsrv.
The network type is TCP.
The user ID is bob.
The password is bobpass.

On a Windows client:

prowin32 odbholder -RO -db sports -dt ODBC -ld mydemo -H host1 -S odbsrv -U bob -P bobpass -Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=sqlserv1

On a UNIX client:

pro odbholder -RO -db sports -dt ODBC -ld mydemo -H host1 -S odbsrv -N TCP -U bob -P bobpass -Dsrv qt_debug,EXTENDED,PRGRS_CONNECT,server=sqlserv1

Note: This configuration assumes you started the remote DataServer broker using the command line interface. To connect to a DataServer broker started through the Progress Explorer you must add the SVUB,1 setting to the -Dsrv parameter and add the -DataService name parameter.